SGI Freeware 1999 August

home *** CD-ROM | disk | FTP | other *** search

/ SGI Freeware 1999 August / SGI Freeware 1999 August.iso / dist / fw_ncurses.idb / usr / freeware / catman / u_man / cat1 / tic.Z / tic

Wrap

Text File | 1999-07-16 | 12.7 KB | 265 lines

ttttiiiicccc((((1111MMMM)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ttttiiiicccc((((1111MMMM)))) NNNNAAAAMMMMEEEE ttttiiiicccc - the _t_e_r_m_i_n_f_o entry-description compiler SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS ttttiiiicccc [----vvvv[_n]] [----wwww[_n]] [----1111hhhhccccppppIIIICCCCNNNNRRRRrrrrssssTTTTuuuu] [----eeee _n_a_m_e_s] [----oooo _d_i_r] _f_i_l_e DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN The command ttttiiiicccc translates a tttteeeerrrrmmmmiiiinnnnffffoooo file from source format into compiled format. The compiled format is necessary for use with the library routines in nnnnccccuuuurrrrsssseeeessss(3X). The results are normally placed in the system terminfo directory @@@@DDDDAAAATTTTAAAADDDDIIIIRRRR@@@@////tttteeeerrrrmmmmiiiinnnnffffoooo. There are two ways to change this behavior. First, you may override the system default by setting the variable TTTTEEEERRRRMMMMIIIINNNNFFFFOOOO in your shell environment to a valid (existing) directory name. Secondly, if ttttiiiicccc cannot get access to @_D_A_T_A_D_I_R@/_t_e_r_m_i_n_f_o or your TERMINFO directory, it looks for the directory $_H_O_M_E/._t_e_r_m_i_n_f_o; if that directory exists, the entry is placed there. Libraries that read terminfo entries are expected to check for a TERMINFO directory first, look at $_H_O_M_E/._t_e_r_m_i_n_f_o if TERMINFO is not set, and finally look in @_D_A_T_A_D_I_R@/_t_e_r_m_i_n_f_o. ----hhhh Print help message and exit. ----cccc specifies to only check _f_i_l_e for errors, including syntax problems and bad use links. If you specify ----CCCC (----IIII) with this option, the code will print warnings about entries which, after use resolution, are more than 1023 (4096) bytes long. Due to a fixed buffer length in older termcap libraries (and a documented limit in terminfo), these entries may cause core dumps. ----vvvv_n specifies that (verbose) output be written to standard error trace information showing ttttiiiicccc's progress. The optional integer _n is a number from 1 to 10, inclusive, indicating the desired level of detail of information. If _n is omitted, the default level is 1. If _n is specified and greater than 1, the level of detail is increased. ----oooo_d_i_r Write compiled entries to given directory. Overrides the TERMINFO environment variable. ----wwww_n specifies the width of the output. Page 1 (printed 5/12/99) ttttiiiicccc((((1111MMMM)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ttttiiiicccc((((1111MMMM)))) ----1111 restricts the output to a single column ----TTTT eliminates size-restrictions on the generated text. This is mainly useful for testing and analysis, since the compiled descriptions are limited (e.g., 1023 for termcap, 4096 for terminfo). ----IIII Force source translation to terminfo format. ----LLLL Force source translation to terminfo format using the long C variable names listed in <tttteeeerrrrmmmm....hhhh> ----CCCC Force source translation to termcap format. Note: this differs from the -C option of _i_n_f_o_c_m_p(1M) in that it does not merely translate capability names, but also translates terminfo strings to termcap format. Capabilities that are not translatable are left in the entry under their terminfo names but commented out with two preceding dots. ----NNNN Disable smart defaults. Normally, when translating from termcap to terminfo, the compiler makes a number of assumptions about the defaults of string capabilities rrrreeeesssseeeetttt1111____ssssttttrrrriiiinnnngggg, ccccaaaarrrrrrrriiiiaaaaggggeeee____rrrreeeettttuuuurrrrnnnn, ccccuuuurrrrssssoooorrrr____lllleeeefffftttt, ccccuuuurrrrssssoooorrrr____ddddoooowwwwnnnn, ssssccccrrrroooollllllll____ffffoooorrrrwwwwaaaarrrrdddd, ttttaaaabbbb, nnnneeeewwwwlllliiiinnnneeee, kkkkeeeeyyyy____bbbbaaaacccckkkkssssppppaaaacccceeee, kkkkeeeeyyyy____lllleeeefffftttt, and kkkkeeeeyyyy____ddddoooowwwwnnnn, then attempts to use obsolete termcap capabilities to deduce correct values. It also normally suppresses output of obsolete termcap capabilities such as bbbbssss. This option forces a more literal translation that also preserves the obsolete capabilities. ----RRRR_s_u_b_s_e_t Restrict output to a given subset. This option is for use with archaic versions of terminfo like those on SVr1, Ultrix, or HP/UX that don't support the full set of SVR4/XSI Curses terminfo; and outright broken ports like AIX that have their own extensions incompatible with SVr4/XSI. Available subsets are "SVr1", "Ultrix", "HP", "BSD" and "AIX"; see tttteeeerrrrmmmmiiiinnnnffffoooo(5) for details. -_r Force entry resolution (so there are no remaining tc capabilities) even when doing translation to termcap format. This may be needed if you are preparing a termcap file for a termcap library (such as GNU termcap up to version 1.3 or BSD termcap up to 4.3BSD) that doesn't handle multiple tc capabilities per entry. -_s Summarize the compile by showing the directory into which entries are written, and the number of entries which are compiled. Page 2 (printed 5/12/99) ttttiiiicccc((((1111MMMM)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ttttiiiicccc((((1111MMMM)))) -_e Limit writes and translations to the following comma- separated list of terminals. If any name or alias of a terminal matches one of the names in the list, the entry will be written or translated as normal. Otherwise no output will be generated for it. The option value is interpreted as a file containing the list if it contains a '/'. (Note: depending on how tic was compiled, this option may require -I or -C.) _f_i_l_e contains one or more tttteeeerrrrmmmmiiiinnnnffffoooo terminal descriptions in source format [see tttteeeerrrrmmmmiiiinnnnffffoooo(5)]. Each description in the file describes the capabilities of a particular terminal. The debug flag levels are as follows: 1 Names of files created and linked 2 Information related to the ``use'' facility 3 Statistics from the hashing algorithm 5 String-table memory allocations 7 Entries into the string-table 8 List of tokens encountered by scanner 9 All values computed in construction of the hash table If n is not given, it is taken to be one. All but one of the capabilities recognized by ttttiiiicccc are documented in tttteeeerrrrmmmmiiiinnnnffffoooo(5). The exception is the uuuusssseeee capability. When a uuuusssseeee=_e_n_t_r_y-_n_a_m_e field is discovered in a terminal entry currently being compiled, ttttiiiicccc reads in the binary from @@@@DDDDAAAATTTTAAAADDDDIIIIRRRR@@@@////tttteeeerrrrmmmmiiiinnnnffffoooo to complete the entry. (Entries created from _f_i_l_e will be used first. If the environment variable TTTTEEEERRRRMMMMIIIINNNNFFFFOOOO is set, that directory is searched instead of @@@@DDDDAAAATTTTAAAADDDDIIIIRRRR@@@@////tttteeeerrrrmmmmiiiinnnnffffoooo.) ttttiiiicccc duplicates the capabilities in _e_n_t_r_y-_n_a_m_e for the current entry, with the exception of those capabilities that explicitly are defined in the current entry. When an entry, e.g., eeeennnnttttrrrryyyy____nnnnaaaammmmeeee____1111, contains a uuuusssseeee====_e_n_t_r_y__n_a_m_e__2 field, any canceled capabilities in _e_n_t_r_y__n_a_m_e__2 must also appear in eeeennnnttttrrrryyyy____nnnnaaaammmmeeee____1111 before uuuusssseeee==== for these capabilities to be canceled in eeeennnnttttrrrryyyy____nnnnaaaammmmeeee____1111. If the environment variable TTTTEEEERRRRMMMMIIIINNNNFFFFOOOO is set, the compiled Page 3 (printed 5/12/99) ttttiiiicccc((((1111MMMM)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ttttiiiicccc((((1111MMMM)))) results are placed there instead of @@@@DDDDAAAATTTTAAAADDDDIIIIRRRR@@@@////tttteeeerrrrmmmmiiiinnnnffffoooo. Total compiled entries cannot exceed 4096 bytes. The name field cannot exceed 128 bytes. Terminal names exceeding 14 characters will be truncated to 14 characters and a warning message will be printed. CCCCOOOOMMMMPPPPAAAATTTTIIIIBBBBIIIILLLLIIIITTTTYYYY There is some evidence that historic ttttiiiicccc implementations treated description fields with no whitespace in them as additional aliases or short names. This ttttiiiicccc does not do that, but it does warn when description fields may be treated that way and check them for dangerous characters. EEEEXXXXTTTTEEEENNNNSSSSIIIIOOOONNNNSSSS Unlike the stock SVr4 ttttiiiicccc command, this implementation can actually compile termcap sources. In fact, entries in terminfo and termcap syntax can be mixed in a single source file. See tttteeeerrrrmmmmiiiinnnnffffoooo(5) for the list of termcap names taken to be equivalent to terminfo names. The SVr4 manual pages are not clear on the resolution rules for uuuusssseeee capabilities. This implementation of ttttiiiicccc will find uuuusssseeee targets anywhere in the source file, or anywhere in the file tree rooted at TTTTEEEERRRRMMMMIIIINNNNFFFFOOOO (if TTTTEEEERRRRMMMMIIIINNNNFFFFOOOO is defined), or in the user's $_H_O_M_E/._t_e_r_m_i_n_f_o directory (if it exists), or (finally) anywhere in the system's file tree of compiled entries. The error messages from this ttttiiiicccc have the same format as GNU C error messages, and can be parsed by GNU Emacs's compile facility. The -o, -I, -C, -N, -R, -h, -e, -T, -r and -s options are not supported under SVr4. The SVr4 -c mode does not report bad use links. System V does not compile entries to or read entries from your $_H_O_M_E/._t_e_r_m_i_n_f_o directory unless TERMINFO is explicitly set to it. FFFFIIIILLLLEEEESSSS @@@@DDDDAAAATTTTAAAADDDDIIIIRRRR@@@@////tttteeeerrrrmmmmiiiinnnnffffoooo////????////**** Compiled terminal description database. SSSSEEEEEEEE AAAALLLLSSSSOOOO iiiinnnnffffooooccccmmmmpppp(1M), ccccaaaappppttttooooiiiinnnnffffoooo(1M), iiiinnnnffffoooottttooooccccaaaapppp(1M), ttttooooeeee(1M), ccccuuuurrrrsssseeeessss(3X), tttteeeerrrrmmmmiiiinnnnffffoooo(5). Page 4 (printed 5/12/99)